v1.19.6

Compare Source

Patch Changes

• #​1246 5d2014f Thanks @​vicb! - fix: do not log expected expected D1 errors

  The populateCache command adds columns to the D1 tag cache for SWR support.
  This is required for older deployments made before those column were added.
  SQLite errors when the columns exist and we should not log those errors.

• #​1244 01babce Thanks @​tahmid-23! - fix: drop streaming wasm calls in Turbopack runtime

  Turbopack replaces wasm imports using WebAssembly.compileStreaming and
  WebAssembly.instantiateStreaming. These functions are not available in
  the workerd runtime.

  We add a helper loadWasmChunkFn. This is a generated switch statement
  that contains an import for each wasm chunk. We use static strings for
  all imports to ensure that all necessary wasm chunks will be detected
  and bundled for the final build.

  The Turbopack patcher replaces the invocations in loadWebAssembly and
  loadWebAssemblyModule, using the synchronous WebAssembly.instantiate
  and redirecting to loadWasmChunkFn.

• #​1243 1c815de Thanks @​tahmid-23! - fix: detect object-valued conditions

  The pre-existing build condition transform logic had subtle errors:

  • failed to recognize object conditions
    (e.g. "workerd": { "import": ..., "require": ... })
  • sibling pruning only applied to strings, not objects

  Now, we fully support object conditions. Furthermore, we prune siblings,
  unless its subtree also contains the build condition.

v10.33.3

Compare Source

v10.33.2

Compare Source

v10.33.1: pnpm 10.33.1

Compare Source

Patch Changes

• When a project's packageManager field selects pnpm v11 or newer, commands that v10 would have passed through to npm (version, login, logout, publish, unpublish, deprecate, dist-tag, docs, ping, search, star, stars, unstar, whoami, etc.) are now handed over to the wanted pnpm, which implements them natively. Previously they silently shelled out to npm — making, for example, pnpm version --help print npm's help on a project with packageManager: pnpm@11.0.0-rc.3 #​11328.

Platinum Sponsors

Gold Sponsors

v10.33.0

Compare Source

v10.32.1: pnpm 10.32.1

Compare Source

Patch Changes

• Fix a regression where pnpm-workspace.yaml without a packages field caused all directories to be treated as workspace projects. This broke projects that use pnpm-workspace.yaml only for settings (e.g. minimumReleaseAge) without defining workspace packages #​10909.

Platinum Sponsors

Gold Sponsors

v10.32.0: pnpm 10.32

Compare Source

Minor Changes

• Added --all flag to pnpm approve-builds that approves all pending builds without interactive prompts #​10136.

Patch Changes

• Reverted change related to setting explicitly the npm config file path, which caused regressions.
• Reverted fix related to lockfile-include-tarball-url. Fixes #​10915.

Platinum Sponsors

Gold Sponsors

v10.31.0

Compare Source

v10.30.3

Compare Source

v10.30.2

Compare Source

v10.30.1: pnpm 10.30.1

Compare Source

Patch Changes

• Use the /-/npm/v1/security/audits/quick endpoint as the primary audit endpoint, falling back to /-/npm/v1/security/audits when it fails #​10649.

Platinum Sponsors

Gold Sponsors

v10.30.0: pnpm 10.30

Compare Source

Minor Changes

• pnpm why now shows a reverse dependency tree. The searched package appears at the root with its dependents as branches, walking back to workspace roots. This replaces the previous forward-tree output which was noisy and hard to read for deeply nested dependencies.

Patch Changes

• Revert pnpm why dependency pruning to prefer correctness over memory consumption. Reverted PR: #​7122.
• Optimize pnpm why and pnpm list performance in workspaces with many importers by sharing the dependency graph and materialization cache across all importers instead of rebuilding them independently for each one #​10596.

Platinum Sponsors

Gold Sponsors

v10.29.3

Compare Source

v8.5.14

Compare Source

• Fixed custom syntax regression (by @​43081j).